home *** CD-ROM | disk | FTP | other *** search
- Date: Mon, 1 Aug 94 01:50 CDT
- From: ekl@sdf.lonestar.org (Evan K. Langlois)
- To: gem-list@world.std.com
- Subject: Re: GEM List
- Precedence: bulk
-
- vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
- Anything that corresponds to something very application-specific should
- be kept in the app's own config file. Auto-save, whatever.
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
- vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
- And again, I don't even very much like the idea of maintianing keys in a
- global file anyway.
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
- More or less to Tim, but everyone should suggestion at end!
-
- Well, since the majority of the vote is AGAINST re-assigning ^A, you had
- better get used to the app-defs.sys file and global keys, because that
- file is gonna save you data. That file is gonna let you make ^A redraw.
- That file is gonna do it all for you. If you can be as insistant about
- USING the app-defs.sys file as you are about re-assigning ^A, then I
- think we should nominate you to talk to ATARI about making AtariWorks
- Gem-list compliant!!!
-
- There needs to be some rule of thumb at least, to say what can and cannot
- be put in the file. I propose this :
-
- If it can change during the course of a running program, then place it
- somewhere else! Otherwise, app-defs is a good spot.
-
-